You are here: BlueCielo Meridian Enterprise Administrator's Guide > About Meridian network administration > Understanding remote access support > Preparing the remote access host computer

Preparing the remote access host computer

The remote access host computers must be configured to display the Offline mode commands in the PowerUser client application. They should synchronize changed documents on every Offline command, but use the remote client computers’ Local Workspace for storage. And for best performance, documents should be viewed using AutoVue Client/Server as described in About AutoVue Client/Server.

If a pool of remote access host computers will be used, the Local Workspace lock ID, which normally identifies the computer where the client is run, must be set to a common value for all of the remote access host computers.

To prepare the remote access host computers for remote access:

  1. If documents that include external references will be edited by remote access client computers, install the documents’ native application on the remote access host computer, which is required to resolve the external references of documents downloaded to the remote access client computers.
  2. Install the Meridian client applications that will be used by the remote access client computers, the appropriate application links, and Application Integration components as described in Installing the client components.
  3. Configure the registry settings described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Client to the values listed in the following table. Create the values if they do not already exist.
Remote access host registry values
Name Type Value

UseCICO

DWORD

1

OfflineMode

DWORD

0

WorkSpaceDB

DWORD

1

Note    If you install the 64-bit edition client components on the remote access host computer, SQL Server Compact Edition must be installed and this value will be set to 1. If the 32-bit edition client components are used on a 64-bit computer, it must be configured to use SQL Server Compact Edition by setting this value to 1. In either case, if SQL Server Compact Edition is not used for the Local Workspace, the Meridian application links will not be available. For more information, see the description of this value in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Client.

WorkSpaceLocation

STRING

\\\\<RemoteResourceName>\\<ShareName>\\<FolderName>

In order for the remote access host computer to store documents on the remote access client computer for editing, the remote access client computer’s drive resources must be accessible through the remote access connection.

This capability goes by different names depending on the remote access software used. For example, the option is named Local Resources in Microsoft Remote Desktop Connection and is enabled by default. To specify a local resource for Microsoft Remote Desktop Connection, replace <RemoteResourceName>  with tsclient and <ShareName> and <FolderName> with appropriate values for the remote access client computers.

If you are using different remote access software, set WorkSpaceLocation to a value that is appropriate for your remote access software and ensure that the local drive resource is shared or mapped accordingly.

WorkSpaceLockID

STRING

<SharedLockID>

If a pool of remote access host computers will be used, set this to a value to be used by all of the remote access host computers, such as Citrix or RemoteDesktop. The value can be anything so long as it is the same for all of the remote access host computers.

Notes

Related concepts

Understanding remote session support

Related tasks

Reserving licenses for remote access

Preparing the Meridian server for remote access

Preparing the remote access client computers


www.bluecieloecm.com